-
Notifications
You must be signed in to change notification settings - Fork 6
fix: Propagate uvicorn logs #1250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1250 +/- ##
==========================================
+ Coverage 94.73% 94.75% +0.02%
==========================================
Files 41 41
Lines 2638 2668 +30
==========================================
+ Hits 2499 2528 +29
- Misses 139 140 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
I struggled to get examples of non-INFO logs, we should make sure some of our obvious use cases that I tried log errors (e.g. searching for a plan that doesn't exist etc.) |

Logs produced by Uvicorn's internals and blueapi are currently processed by different handlers. Due to this nothing produced by Uvicorn is being propagated to Graylog.
This PR relegates handling of Uvicorn logs to BlueAPI's handlers and standardises terminal formatting.
Fixes #1248